-
Notifications
You must be signed in to change notification settings - Fork 12
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Using CoAP with Node-RED for Low-Power Devices #2422
base: main
Are you sure you want to change the base?
Conversation
Images automagically compressed by Calibre's image-actions ✨ Compression reduced images by 43.5%, saving 19.11 KB.
1284 images did not require optimisation. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Overall, the article reads will and is nicely written however I have 2 concerns with releasing this material.
-
Unrealistic "Why does it matter" argument. A Rasperry Pi can only run on batteries for a matter of hours (obviously depending on battery size, RPi type and workload) - however we are talking 10s of hours not days or weeks - just feels a little unrealistic and I dont think we should be publishing that kind of documentation if I am honest.
-
The table of data rates reads great but there is no reference to how we came to these numbers or proofs. The numbers "feel" a bit "perfect" and without any reference to WireShark or our methods, I am hesitant to include such detail. I would either hope to see hard facts to accompany this OR a slimmed down "potential benefits" kind of data
Yes, I agree. There is one more reason why I am not considering publishing this article: the node is not working properly right now, as some of its features do not function correctly. |
That's why I haven't followed up for its review. I think we should close this PR. |
Happy to close it if the node package is not working well. Out of interest, what issues did you find? Did you note if the node package had an issue tracker and what the authors responsiveness was? |
The author is active in merging dependency bot PRs but has not been adding new features or fixing existing issues. The CoAP node has several problems: it doesn't support IPv6 (even though there is an option for it), the agent functionality isn't working, and it lacks support for multicast and conformability( even this option is provided. Additionally, there's a field to set the timeout, but it doesn't work properly—when you try to input a value, it gets wiped out. |
Description
Related Issue(s)
Checklist